Auto-waking of a suspended os in a dockable system

ABSTRACT

A mobile computing device with a mobile operating system and desktop operating system running concurrently and independently on a shared kernel without virtualization. The mobile operating system provides a user experience for the mobile computing device that suits the mobile environment. The desktop operating system provides a full desktop user experience when the mobile computing device is docked to a secondary terminal environment. The desktop operating system may be suspended when the mobile computing device is not docked with a secondary terminal environment and resumed when the mobile computing device is docked with a secondary terminal environment that provides a desktop computing experience. The mobile computing device may be a smartphone running the Android mobile OS and a full desktop Linux OS distribution on a modified Android kernel.

CROSS-REFERENCE TO RELATED APPLICATIONS

This Application is a non-provisional of and claims the benefit of the filing date of U.S. Provisional Application Nos. 61/389,117, filed Oct. 1, 2010, entitled “Multi-Operating System Portable Docking Device”; 61/507,201, filed Jul. 13, 2011, entitled “Cross-Environment Communication Framework”; 61/507,203, filed Jul. 13, 2011, entitled “Multi-Operating System”; 61/507,206, filed Jul. 13, 2011, entitled “Auto-Configuration of a Docked System in a Multi-OS Environment”; and 61/507,209, filed Jul. 13, 2011, entitled “Auto-Waking of a Suspended Secondary OS in a Dockable System,” wherein the entire contents of the foregoing priority applications are incorporated herein by reference for all purposes.

BACKGROUND

1. Field

This Application relates generally to the field of mobile computing environments, and more particularly to supporting multiple user environments through the use of multiple operating systems in a single mobile computing device.

2. Relevant Background

Mobile computing devices are becoming ubiquitous in today's society. For example, as of the end of 2008, 90 percent of Americans had a mobile wireless device. At the same time, the capabilities of mobile devices are advancing rapidly, including smartphones that integrate advanced computing capabilities with mobile telephony capabilities. Mobile providers have launched hundreds of new smartphones in the last three years based upon several different platforms (e.g., Apple iPhone, Android, BlackBerry, Palm, and Windows Mobile). In the U.S., smartphone penetration reached almost 23% by the middle of 2010, and over 35% in some age-groups. In Europe, the smartphone market grew by 41% from 2009 to 2010, with over 60 million smartphone subscribers as of July 2010 in the five largest European countries alone.

While smartphones are gaining in popularity and computing capability, they provide a limited user experience. Specifically, they typically have an operating system that is modified for mobile device hardware and a restricted set of applications that are available for the modified operating system. For example, many smartphones run Google's Android operating system. Android runs only applications that are specifically developed to run within a Java-based virtual machine runtime environment. In addition, while Android is based on a modified Linux kernel, it uses different standard C libraries, system managers, and services than Linux. Accordingly, applications written for Linux do not run on Android without modification or porting. Similarly, Apple's iPhone uses the iOS mobile operating system. Again, while iOS is derived from Mac OS X, applications developed for OS X do not run on iOS. Therefore, while many applications are available for mobile operating systems such as Android and iOS, many other common applications for desktop operating systems such as Linux and Mac OS X are not available on the mobile platforms.

Accordingly, smartphones are typically suited for a limited set of user experiences and provide applications designed primarily for the mobile environment. In particular, smartphones do not provide a suitable desktop user experience, nor do they run most common desktop applications. As a result, many users carry and use multiple computing devices including a smartphone, laptop, and/or tablet computer. In this instance, each device has its own CPU, memory, file storage, and operating system.

Connectivity and file sharing between smartphones and other computing devices involves linking one device (e.g., smartphone, running a mobile OS) to a second, wholly disparate device (e.g., notebook, desktop, or tablet running a desktop OS), through a wireless or wired connection. Information is shared across devices by synchronizing data between applications running separately on each device. This process, typically called “synching,” is cumbersome and generally requires active management by the user.

SUMMARY

Embodiments of the present invention are directed to providing the mobile computing experience of a smartphone and the appropriate user experience of a secondary terminal environment in a single mobile computing device. A secondary terminal environment may be some combination of visual rendering devices (e.g., monitor or display), input devices (e.g., mouse, touch pad, touch-screen, keyboard, etc.), and other computing peripherals (e.g., HDD, optical disc drive, memory stick, camera, printer, etc.) connected to the computing device by a wired (e.g., USB, Firewire, Thunderbolt, etc.) or wireless (e.g., Bluetooth, WiFi, etc.) connection. In embodiments, a mobile operating system associated with the user experience of the mobile environment and a desktop operating system associated with the user experience of the secondary terminal environment are run concurrently and independently on a shared kernel.

According to one aspect consistent with various embodiments, a mobile computing device is running a mobile operating system in a first execution environment on a shared kernel and concurrently running a desktop operating system in a second execution environment on the shared kernel. The mobile computing device is configured to multiple user environments by detecting, in the mobile computing device, a docking event of the mobile computing device with a secondary terminal environment, determining that a user experience profile of the docked secondary terminal environment is associated with the desktop operating system, and resuming, in response to determining that the user experience profile of the docked secondary terminal environment is associated with the desktop operating system, the desktop operating system from a suspended condition.

According to other aspects consistent with various embodiments, determining whether the user experience profile of the docked secondary terminal environment is associated with the desktop operating system includes receiving, in a desktop monitor service of the mobile operating system, a notification of a docking event from the shared kernel, and determining, by the desktop monitor service, that the user experience profile of the docked secondary terminal environment is associated with the desktop operating system. Resuming the desktop operating system may include receiving, in a daemon process of the desktop operating system, a call to a remotable object, the call to the remotable object including an action, and performing the action in the daemon process of the desktop operating system. The mobile computing device may receive an indicator of the user experience profile of the secondary terminal environment from a dock connector. The user experience profile of the secondary terminal environment may be based on predefined criteria associated with one or more input or output devices of the secondary terminal environment. The predefined criteria may include a resolution of a display device of the secondary terminal environment and/or a character input device type criteria. The desktop operating system may be associated with the docked secondary terminal environment. The secondary terminal environment may include a display device, a keyboard, and a pointing device.

According to other aspects consistent with various embodiments, a mobile computing device is running a mobile operating system in a first execution environment on a shared kernel and concurrently running a desktop operating system in a second execution environment on the shared kernel. The mobile computing device is configured to multiple user environments by registering a daemon process of the desktop operating system through an inter-process communication channel in the shared kernel to receive remotable objects from a desktop monitor service of the mobile operating system, detecting a docking event of the mobile computing device with a secondary terminal environment, notifying the desktop monitor service of the mobile operating system of the docking event, determining, by the desktop monitor service, an action to be performed by the daemon process of the desktop operating system based on a user experience profile of the docked secondary terminal environment, and sending, from the desktop monitor service to the daemon process of the desktop operating system through the inter-process communication channel, the action to be performed.

According to other aspects consistent with various embodiments, the user experience profile of the docked secondary terminal environment may be associated with the desktop operating system and the action to be performed may comprise resuming the desktop operating system from a suspended condition. The docked secondary terminal environment may be associated with the desktop operating system. Alternatively, the user experience profile of the docked secondary terminal environment may be associated with the mobile operating system and the action to be performed may comprise suspending the desktop operating system. The docked secondary terminal environment may be associated with the mobile operating system.

According to other aspects consistent with various embodiments, a mobile computing device is running a mobile operating system in a first execution environment on a shared kernel and concurrently running a desktop operating system in a second execution environment on the shared kernel. The mobile computing device may be configured to multiple user environments by detecting, in the mobile computing device, a docking event of the mobile computing device with a secondary terminal environment, determining that the mobile computing device is not docked to a secondary terminal environment, and suspending, in response to determining that the mobile computing device is not docked to a secondary terminal environment, the desktop operating system. The docking event may comprise undocking the mobile computing device from a secondary terminal environment. Suspending the desktop operating system may comprise receiving, in a daemon process of the desktop operating system, a call to a remotable object, the call to the remotable object including an action, and performing the action in the daemon process of the desktop operating system.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention are illustrated in referenced figures of the drawings, in which like numbers refer to like elements throughout the description of the figures.

FIG. 1 illustrates a computing environment that provides multiple user computing experiences, according to various embodiments.

FIG. 2 illustrates an exemplary system architecture for a mobile computing device, according to various embodiments.

FIG. 3 illustrates an operating system architecture for a computing environment, according to various embodiments.

FIG. 4 illustrates aspects of a mobile operating system for a computing environment, according to various embodiments.

FIG. 5 illustrates aspects of shared kernel for a computing environment, according to various embodiments.

FIG. 6 illustrates aspects of a desktop operating system for a computing environment, according to various embodiments.

FIG. 7 illustrates an exemplary boot procedure that may be used to configure an operating system architecture of a mobile computing device, according to various embodiments.

FIG. 8 illustrates a process flow for detecting and responding to docking events, according to various embodiments.

FIG. 9 illustrates one configuration of an operating system architecture for a computing environment, according to various embodiments.

FIG. 10 illustrates another configuration of an operating system architecture for a computing environment, according to various embodiments.

FIG. 11 illustrates another configuration of an operating system architecture for a computing environment, according to various embodiments.

FIG. 12 illustrates a computing environment that may include multiple computing experiences, according to various embodiments.

DETAILED DESCRIPTION

Traditionally, handheld mobile telephony devices (i.e., “handsets”) were developed independently and served a separate and distinct purpose from that of personal computers (“PCs”) such as desktops and laptops. Handheld mobile telephony devices were focused primarily on communication while PCs were focused on computing tasks such as creating and editing documents, text-based communication (e.g., email, etc.), multimedia, and web browsing. However, mobile telephony devices are including ever-increasing computing ability and users increasingly desire convergence of communication and computing capabilities into multi-use mobile devices.

For example, mobile telephony devices called “smartphones” that include computing capabilities are increasing in popularity. Many of these smartphones include a mobile operating system (“OS”) running on a mobile processor. While mobile processors and mobile OS's have increased the capabilities of these devices, smartphones have not tended to replace PC environments such as desktop or notebook computers at least because of the limited user experience provided. In particular, for some tasks such as typing or editing documents, a full-size keyboard and large display are easier to use than the user interface components typically found on a smartphone. For example, smartphones typically use a small thumb-style QWERTY keyboard, touch-screen display, click-wheel, and/or scroll-wheel as user interface components. Selecting menu options or items typically involves either using a touch-screen display, or using the click-wheel or scroll-wheel to navigate menus and select items. This interface is suited to the small display screens and limited menu options typically found in smartphones, but not suited to controlling more traditional programs with a larger number of menu options, larger screen area, and user interface built around a pointing device such as a traditional mouse.

In embodiments, a mobile computing device automatically detects a docked environment and wakes up a suspended, full-featured, secondary operating system for use in the docked environment. In one implementation, a mobile operating system and a desktop operating system run concurrently on a single shared kernel on a mobile computing device. When the mobile computing device is not docked the mobile operating system drives the mobile device display, etc., and the desktop operating system is in a suspended mode (e.g., processes of the desktop operating system are suspended and do not consume computing resources). When the mobile computing device is docked with a secondary terminal environment having a user experience profile associated with the desktop operating system, the mobile device automatically detects the secondary terminal environment and wakes up the desktop operating system to support the secondary terminal environment.

FIG. 1 illustrates a computing environment 100 that provides multiple user computing experiences, according to various embodiments. Computing environment 100 includes mobile computing device 110. Mobile computing device 110 includes mobile computing hardware and software components. Hardware components of mobile computing device 110 include mobile processor 114, display 116, I/O device(s) 118, and/or port 120. Software components of mobile computing device 110 include a first OS 130 and a second OS 160. In one embodiment, first OS 130 is a mobile OS and second OS 160 is a desktop OS. When mobile computing device 110 is operated as a stand-alone mobile device, mobile OS 130 presents a typical mobile computing user experience through display 116 and I/O device(s) 118. The mobile computing experience provided by mobile OS 130 typically includes mobile telephony capabilities and a graphical user interface (“GUI”) suited to the mobile environment including display 116 and I/O device(s) 118. For example, display 116 may be a touch-screen display and application programs (i.e., “Apps”) running on mobile OS 130 may be controlled through the GUI of mobile OS 130 on touch-screen display 116.

Mobile computing device 110 may be connected to I/O devices 144, 146 and/or 148 through port 120. I/O devices 144, 146, and/or 148 may make up a secondary terminal environment 140. In some instances, secondary terminal environment 140 may be more suited to desktop OS 160 than mobile OS 130. For example, secondary terminal environment 140 may include a keyboard 144, pointing device 146, and a display device 148. In these instances, desktop OS 160 can be associated with secondary terminal environment 140 to provide the full capabilities of a notebook or desktop computer environment through secondary terminal environment 140. In other instances, secondary terminal environment 140 may be more suited for mobile OS 130 than desktop OS 160. For example, secondary terminal environment 140 may include a touch-screen display. In these instances, mobile OS 130 may be associated with secondary terminal environment 140.

In FIG. 1, port 120 is shown as connected to port 142 of secondary terminal environment 140 through interface 120. However, port 120 may include separate connections to each I/O device 144, 146 and 148 through interface 122. Interface 122 may be any suitable wired or wireless interface or combination of wired and wireless interfaces for connecting devices such as keyboards, monitors, pointing devices, etc. For example, interface 122 may be a combination of a display interface (e.g., VGA, DVI, HDMI, etc.) and a device communications interface (e.g., USB, Bluetooth, Firewire, other serial communications interface, etc.). Alternatively, interface 122 may be a single communications interface that supports both video and device communications signals (e.g., Thunderbolt, etc.).

Traditionally, the hardware and software development paths for the handset environment and the PC environment have been completely independent because of different use models and competing constraints on product design. PCs, including desktop and laptop computers, are designed to be flexible and powerful. Specifically, PC hardware architecture is typically based around a general purpose PC processor connected to memory, graphics, and external components through various general purpose interfaces on a motherboard. For example, a personal computer motherboard may include a processor connected through a logic chipset to a graphics processor, system memory (e.g., RAM), and various other components through communication interfaces (PCI, USB, ISA, IDE, etc.). Some more highly integrated PC processors include an interface to a graphics processor (e.g., AGP, etc.) and/or interface to system memory (e.g., SDR, DDR, DDR2, DDR3, DRDRAM, etc.) on the processor.

PC processors are optimized for high processor clock speed and computationally intensive tasks. The personal computer market is presently dominated by processors based on the x86 CPU architecture. Current x86-based PC processors for desktop computers have multiple 64-bit central processing units (‘CPUs”) (or “cores”) with clock speeds exceeding 2.5 GHz and power consumption approaching 100 Watts. Current x86-based PC processors for laptop computers typically run at clock speeds up to 2.0 GHz and have power consumption in the range of 15-45 Watts. Because of the large power consumption of these processors, desktop and laptop computers may require cooling devices such as fans or heat-sinks to remove waste heat from the processor. In addition, the battery life of laptop computers using x86-based PC processors is typically less than four hours.

In contrast, mobile processors for handsets are optimized for low power consumption and a high level of integration to reduce the overall size of the handset. For example, mobile processors for handsets such as smartphones typically run at clock speeds lower than 2.0 GHz, have power consumption of less than 1 Watt, and integrate functions common to the mobile environment such as graphics controllers, communications interfaces, and camera controllers. The most common mobile processor architectures are reduced instruction set computing (“RISC”) processor architectures. Specifically, the “ARM” mobile processor architecture is currently the predominant architecture for mobile processors designed for smartphones and other ultra-portable and low power computing devices. Some PC processor manufacturers also refer to PC processors designed for use in laptop computers as “mobile processors.” However, as used herein, the term “mobile processor” refers to a processor suited for use in a handset or smartphone, typically consuming less than 1 Watt and integrating mobile functionality.

Personal computers and handsets also typically have different system resources, input/output (“I/O”) devices, and peripherals. For example, desktop and laptop computers typically have much larger amounts of system memory and storage capacity than handsets. While a typical laptop computer may have more than 2 GB of RAM and a hard-drive with a capacity of more than 250 GB, handsets typically have less than 512 MB of RAM and a solid-state drive with a capacity of less than 32 GB. User interface components of personal computers typically include a display screen larger than 9 inches diagonally, a full keyboard, and pointing device(s) for user input. In contrast, handsets typically include a display screen smaller than 7 inches diagonally and user interface components such as a thumb-style QWERTY keyboard, touch-screen display, click-wheel, and/or scroll-wheel. Peripherals found on personal computers typically include an optical disk drive (e.g., CD, DVD, DVD-RW, etc.), expansion ports (e.g., PCMCIA, SCSI, Express Card, etc.), video output port (e.g., VGA, DVI, HDMI, etc.), and generic device ports (e.g., USB, etc.). In contrast, handsets typically do not have optical disk drives or expansion ports. However, other devices are typically integrated into handsets including wireless communications interface(s) (e.g., GSM, CDMA, LTE, EDGE, WiFi, WiMax, etc.), GPS chipset, accelerometer, camera(s), and/or solid-state memory port (SD, Memory Stick, etc.).

Software for personal computers and handsets has also traditionally been developed independently. For example, personal computers including desktops and laptops typically run different operating systems than mobile devices. An operating system is software that manages computer hardware and resources and provides common services for execution of applications software on the computer hardware. Operating systems are generally described as having various abstraction layers, where each layer interfaces with the layer below through an interface.

Generally, the kernel of an operating system refers to the core OS layer that manages the computing devices resources such as the CPU(s) (CPU scheduling), memory, and I/O (including peripheral and file system access). A kernel will usually provide features for low-level scheduling of processes (dispatching), inter-process communication, process synchronization, context switching, manipulation of process control blocks, interrupt handling, process creation and destruction, and process suspension and resumption. The OS kernel may or may not include device drivers. Other layers of the OS interface with the kernel through system calls or an application programming interface (“API”) layer.

Generally, other OS layers include the libraries layer, application framework layer, and application layer. The libraries layer typically includes system libraries and other user libraries. The application framework layer includes services, managers, and runtime environments. The application layer includes user applications, which may run within a runtime environment of the application framework layer. A user interacts with the OS through the OS GUI. The GUI presents menus, buttons, and controls that the user selects to control and use applications running on the OS. Commonly, the term “desktop environment” is used to refer to a style of GUI through which the user interfaces with the OS using icons, windows, toolbars, folders, and/or desktop widgets, and is not limited to a desktop OS. For example, a mobile OS could have a desktop environment, referring to the look and feel of the mobile OS GUI.

Operating systems for personal computers (desktop OSs) were designed for multi-tasking, larger screen areas, and to provide a flexible environment for application developers. As used herein, the term desktop OS refers to an operating system designed for use with a personal computer environment, for example a desktop or laptop use environment. Examples of desktop OS's include various distributions of Linux, Mac OS X, and Windows 7, among many others.

Operating systems for mobile devices (mobile OSs) were developed for the smaller screen area, lower processing power, smaller memory, and smaller disk space typically found on handsets and smartphones. Example mobile OSs include Android, Apple's iOS (for the iPhone and iPad), Microsoft's Windows Mobile (superseded by Windows Phone 7), Nokia's Symbian, and Palm's Palm OS (superseded by HP webOS). As used herein, the term mobile OS refers to an operating system designed for use with a mobile environment including running on a low-power processor with reduced system resources compared to the PC environment (i.e., desktop or laptop computer system).

Mobile operating systems generally have a particular application development environment that is used to create application programs (i.e., “apps”) that run on the mobile OS. The application development environment both facilitates application development by providing common tools and APIs for accessing system resources and services, and limits what applications are allowed to do such that the mobile device is able to continue to provide other required functions. For example, incoming phone calls and texts may interrupt a running application to notify the user of the incoming call or text.

The most widely adopted mobile OS is Google's Android. While Android is based on Linux, it includes modifications to the kernel and other OS layers for the mobile environment and mobile processors. In particular, while the Linux kernel is designed for the x86 CPU architecture, the Android kernel is modified for ARM-based mobile processors. Android device drivers are also particularly tailored for devices typically present in a mobile hardware architecture including touch-screens, mobile connectivity (GSM/EDGE, CDMA, Wi-Fi, etc.), battery management, GPS, accelerometers, and camera modules, among other devices.

In Android, applications run within the Dalvik virtual machine on an object-oriented application framework designed specifically for the memory and processor speed constraints of mobile hardware architectures. Applications are developed for the Dalvik virtual machine through the Android SDK. In addition, Android does not have a native X Window System nor does it support the full set of standard GNU libraries, and this makes it difficult to port existing GNU/Linux applications or libraries to Android.

Apple's iOS operating system (run on the iPhone) and Microsoft's Windows Phone 7 are similarly modified for the mobile environment and mobile hardware architecture. For example, while iOS is derived from the Mac OS X desktop OS, common Mac OS X applications do not run natively on iOS. Specifically, applications are developed for iOS through an SDK to run within the “Cocoa Touch” runtime environment of iOS, which provides basic application infrastructure and support for key iOS features such as touch-based input, push notifications, and system services. Therefore, applications written for Mac OS X do not run on iOS without porting them through the iOS SDK. In addition, it may be difficult to port Mac OS X applications to iOS because of differences between user libraries and application framework layers of the two OSs, and differences in system resources of the mobile and desktop hardware.

Because of the differences in processing requirements, system resources, and application development, applications developed for desktop OSs typically do not run on mobile OSs. Additionally, desktop applications may not be easily ported to mobile OSs because they are optimized for a larger screen area, more processing speed, more system memory, different libraries, and commonly a different GUI. As a result, users typically use separate computing devices for each user environment, including a smartphone, tablet computer, laptop computer, and/or desktop computer. In this instance, each device has its own CPU, memory, file storage, and OS.

Connectivity and file sharing between smartphones and other devices involves linking one device (e.g., smartphone, running a mobile OS) to a second, wholly disparate device (e.g., notebook, desktop, or tablet running a desktop OS), through a wireless or wired connection. Information is shared across devices by synchronizing data between applications running separately on each device. This process, typically called “synching,” is cumbersome and generally requires active management by the user.

Recently, some attempts have been made to provide a more complete user experience with a single mobile computing device. For example, a smartphone may be connected to an external monitor and input devices such as a full keyboard to provide a more desktop-like user experience, with the mobile OS graphical user interface extended to the larger screen and accepting input from the input devices. However, because the external monitor and input devices are only an extension of the smartphone's operating system and user interface, the capabilities of the docked environment are limited by the smartphone's mobile OS. For example, many software applications available on desktop OSs are not available or have limited functionality on mobile OSs. Accordingly, these devices do not present a full desktop user experience when connected to an external environment.

Referring still to FIG. 1, computing environment 100 provides multiple user computing experiences without the above limitations. Specifically, because mobile computing device 110 includes multiple OSs, where each OS is suited to a particular computing environment, mobile computing device 110 may be adapted with external devices to provide a broad range of user experiences with a single mobile computing device. For example, a user may have a mobile computing device 110 and a secondary terminal environment 140 that provides the user experience of a laptop when connected to mobile computing device 110. In this instance, desktop OS 160 of the mobile computing device is associated with the secondary terminal environment 140 when the secondary terminal environment is connected to mobile computing device 110. To the user, the full capabilities of desktop OS 160 are available through secondary terminal environment 140.

FIG. 2 illustrates an exemplary hardware system architecture for mobile computing device 110, according to various embodiments. Mobile computing device hardware 112 includes mobile processor 114 that includes one or more CPU cores 204 and external display interface 220. Generally, mobile computing device hardware 112 also includes I/O device(s) 118, memory 206, storage device(s) 208, touch-screen display controller 210 connected to touch-screen display 116, power management IC 214 connected to battery 216, cellular modem 218, communication device(s) 222, and/or other device(s) 224 that are connected to processor 114 through various communication signals and interfaces. I/O device(s) 118 generally includes buttons and other user interface components that may be employed in mobile computing device 110. For example, I/O device(s) 118 may include a set of buttons, (e.g., back, menu, home, search, etc.), off-screen gesture area, click-wheel, scroll-wheel, QWERTY keyboard, etc. Other device(s) 224 may include, for example, GPS devices, LAN connectivity, microphones, speakers, cameras, accelerometers, and/or MS/MMC/SD/SDIO card interfaces. External display interface 220 may be any suitable display interface (e.g., VGA, DVI, HDMI, etc.).

Processor 114 may be an ARM-based mobile processor. In embodiments, mobile processor 114 is a mobile ARM-based processor such as Texas Instruments OMAP3430, Marvell PXA320, Freescale iMX51, or Qualcomm QSD8650/8250. However, mobile processor 114 may be another suitable ARM-based mobile processor or processor based on other processor architectures such as, for example, x86-based processor architectures or other RISC-based processor architectures.

While FIG. 2 illustrates one exemplary hardware implementation 112 for mobile computing device 110, other architectures are contemplated as within the scope of the invention. For example, various components illustrated in FIG. 2 as external to mobile processor 114 may be integrated into mobile processor 114. Optionally, external display interface 220, shown in FIG. 2 as integrated into mobile processor 114, may be external to mobile processor 114. Additionally, other computer architectures employing a system bus, discrete graphics processor, and/or other architectural variations are suitable for employing aspects of the present invention.

FIG. 3 illustrates OS architecture 300 that may be employed to run mobile OS 130 and desktop OS 160 concurrently on mobile computing device 110, according to various embodiments. As illustrated in FIG. 3, mobile OS 130 and desktop OS 160 are independent operating systems. Specifically, mobile OS 130 and desktop OS 160 may have independent and incompatible user libraries and/or framework layers. Functions and instructions for OS architecture 300 may be stored as computer program code on a tangible computer readable medium of mobile computing device 110. For example, instructions for OS architecture 300 may be stored in storage device(s) 208 of mobile computing device hardware 112.

As illustrated in FIG. 3, mobile OS 130 has libraries layer 330, application framework layer 340, and application layer 350. In mobile OS 130, applications 352 and 354 run in application layer 350 supported by application framework layer 340 of mobile OS 130. Application framework layer 340 includes manager(s) 342 and service(s) 344 that are used by applications running on mobile OS 130. For example, application framework layer 340 may include a window manager, activity manager, package manager, resource manager, telephony manager, gesture controller, and/or other managers and services for the mobile environment. Application framework layer 340 may include a mobile application runtime environment that executes applications developed for mobile OS 130. The mobile application runtime environment may be optimized for mobile computing resources such as lower processing power or limited memory space. The mobile application runtime environment may rely on the kernel for process isolation, memory management, and threading support. Libraries layer 330 includes user libraries 332 that implement common functions such as I/O and string manipulation (“standard C libraries”), graphics libraries, database libraries, communication libraries, and/or other libraries.

As illustrated in FIG. 3, desktop OS 160 has libraries layer 360, framework layer 370, and application layer 380. In desktop OS 160, applications 382 and 384 run in application layer 380 supported by application framework layer 370 of desktop OS 160. Application framework layer 370 includes manager(s) 372 and service(s) 374 that are used by applications running on desktop OS 160. For example, application framework layer 370 may include a window manager, activity manager, package manager, resource manager, and/or other managers and services common to a desktop environment. Libraries layer 360 may include user libraries 362 that implement common functions such as I/O and string manipulation (“standard C libraries”), graphics libraries, database libraries, communication libraries, and/or other libraries.

In various embodiments of the present disclosure, desktop OS 160 runs in a separate execution environment from mobile OS 130. For example, mobile OS 130 may run in a root execution environment and desktop OS 160 may run in a secondary execution environment established under the root execution environment. Processes and applications running on mobile OS 130 access user libraries 332, manager(s) 342 and service(s) 344 in the root execution environment. Processes and applications running on desktop OS 160 access user libraries 362, manager(s) 372 and service(s) 374 in the secondary execution environment.

Generally applications developed for mobile OS 130 do not run directly on desktop OS 160, and applications developed for desktop OS 160 do not run directly on mobile OS 130. For example, application 382 running in application layer 380 of desktop OS 160 may be incompatible with mobile OS 130, meaning that application 382 could not run on mobile OS 130. Specifically, application 382 may use manager(s) 372 and service(s) 374 of application framework layer 370 of desktop OS 160 that are either not available or not compatible with manager(s) 342 and service(s) 344 in application framework layer 340 in mobile OS 130. In addition, application 382 may attempt to access user libraries 362 that exist in libraries layer 360 of desktop OS 160 but are either not available or not compatible with user libraries 332 available in libraries layer 330 of mobile OS 130.

In OS architecture 300, mobile OS 130 and desktop OS 160 run concurrently on shared kernel 320. This means that mobile OS 130 and desktop OS 160 are running on shared kernel 320 at the same time. Specifically, mobile OS 130 and desktop OS 160 both interface to shared kernel 320 through the same kernel interface 322, for example, by making system calls to shared kernel 320. Shared kernel 320 manages task scheduling for processes of both mobile OS 130 and desktop OS 160. In this regard, mobile OS 130 and desktop OS 160 are running independently and concurrently on shared kernel 320. In addition, shared kernel 320 runs directly on mobile processor 114 of mobile computing device hardware 112, as illustrated by hardware interface 312. Specifically, shared kernel 320 directly manages the computing resources of mobile computing device hardware 112 such as CPU scheduling, memory access, and I/O. In this regard, hardware resources are not virtualized, meaning that mobile OS 130 and desktop OS 160 make system calls through kernel interface 322 without virtualized memory or I/O access.

There are several known techniques for providing multiple OS's on the same computing device. However, none of these techniques provide multiple different OS's running concurrently and independently on a shared kernel. More particularly, none of these techniques provide a solution for a mobile OS and a desktop OS running on a shared kernel.

In one technique, known as dual-boot, multiple OS's are loaded on the computing device one at a time. For example, at boot time, a user may select one OS from multiple available OSs to be run on the device, where each OS has its own kernel, libraries, framework, and applications. The system then boots up into that operating system and the other OS(s) are not running (i.e., no processes of the other OS(s) are loaded concurrently with the running OS). Therefore, this technique does not run multiple OS's on a shared kernel, nor does this technique run multiple OSs concurrently.

Another technique for running multiple OS's on the same device is to use a Virtual Machine Manager (“VMM”), or “Hypervisor.” A VMM or Hypervisor runs directly on the hardware and separates the individual kernels of each OS from the hardware, controlling which computer hardware resources are available to each OS at any given time. A Hypervisor effectively creates multiple virtual machines from one device, such that each OS sees a separate virtual machine. Therefore, multiple OSs running on the same device through Hypervisor and VMM are not running on a shared kernel. The Hypervisor adds system overhead due to each OS having to access system resources through virtualization in the Hypervisor. Additionally, because the Hypervisor must allocate CPU and other computing resources, each OS may not be able to effectively schedule processes and tasks.

Yet another technique for running multiple OSs on the same device is to use a hosted virtual machine. In this technique, each OS has its own kernel, with the kernel of the guest OS running on a virtual machine in the host OS. The virtual machine may be a virtualized hardware platform different than the physical hardware platform. The virtual machine in the host OS may be implemented in the kernel of the host OS. In this instance, the kernel of the host OS acts as a hypervisor through which the kernel of the guest OS accesses the processor and hardware resources. Regardless of where the virtual machine is implemented in this technique, the host OS and the guest OS have separate kernels. Therefore, hosted virtual machines do not have multiple OSs running on a shared kernel. System performance using this technique may be reduced due to virtualization of hardware resources for the guest OS.

Another form of virtualization is operating system level virtualization. In this technique, multiple isolated user-space instances may be created on the kernel of an operating system, which look like separate OS instances from the point of view of users of each user-space instance. In this technique, the host OS and guest OS(s) must be the same OS. Accordingly, this technique does not provide a solution for a mobile OS and desktop OS running independently and concurrently on a shared kernel. Further, similarly to a hosted virtual machine, this technique uses disk space and memory virtualization for the guest OS(s). Accordingly, this technique does not provide direct access to memory and system resources for each concurrent OS.

These techniques of running multiple OS's have limitations with regard to running both operating systems concurrently and independently. For example, virtualization involves setting up a distinct address space for the guest OS and simulating I/O to the guest OS. Therefore, access to hardware including system memory has higher overhead for the guest OS using virtualization. Additionally, techniques using Hypervisors result in lack of certainty in process control of each OS. Specifically, the Hypervisor manages the amount of CPU time allocated to each OS, and each OS then allocates CPU time for processes within the OS, without knowledge of what is occurring in the other OS. In this regard, high priority processes within one OS may not be given the required CPU time to complete their tasks because the OS is sharing CPU time through the Hypervisor, which cannot account for the relative priorities of processes running within each OS. Because processing power may be limited in mobile processor architectures relative to desktop processor architectures, techniques that depend on virtualization, including hypervisors, and operating system level virtualization, may not offer optimal performance for a desktop OS running concurrently with a mobile OS on a mobile processor.

In one embodiment consistent with OS architecture 300, an Android mobile OS and a full Linux OS run independently and concurrently on a modified Android kernel. In this embodiment, the Android OS may be a modified Android distribution while the Linux OS (“Hydroid”) is a modified Debian Linux desktop OS. FIGS. 4-6 illustrate Android mobile OS 430, Android kernel 520, and Hydroid OS 660 that may be employed in OS architecture 300 in more detail.

As illustrated in FIG. 4, Android OS 430 includes a set of C/C++ libraries in libraries layer 432 that are accessed through application framework layer 440. Libraries layer 432 includes the “bionic” system C library 439 that was developed specifically for Android to be smaller and faster than the “glibc” Linux C-library. Libraries layer 432 also includes inter-process communication (“IPC”) library 436, which includes the base classes for the “Binder” IPC mechanism of the Android OS. Binder was developed specifically for Android to allow communication between processes and services. Other libraries shown in libraries layer 432 in FIG. 4 include media libraries 435 that support recording and playback of media formats, surface manager 434 that managers access to the display subsystem and composites graphic layers from multiple applications, 2D and 3D graphics engines 438, and lightweight relational database engine 437. Other libraries that may be included in libraries layer 432 but are not pictured in FIG. 4 include bitmap and vector font rendering libraries, utilities libraries, browser tools (i.e., WebKit, etc.), and/or secure communication libraries (i.e., SSL, etc.).

Application framework layer 440 of Android OS 430 provides a development platform that allows developers to use components of the device hardware, access location information, run background services, set alarms, add notifications to the status bar, etc. Framework layer 440 also allows applications to publish their capabilities and make use of the published capabilities of other applications. Components of application framework layer 440 of Android mobile OS 430 include activity manager 441, resource manager 442, window manager 443, dock manager 444, hardware and system services 445, desktop monitor service 446, multi-display manager 447, and remote communication service 448. Other components that may be included in framework layer 440 of Android mobile OS 430 include a view system, telephony manager, package manager, location manager, and/or notification manager, among other managers and services.

Applications running on Android OS 430 run within the Dalvik virtual machine 431 in the Android runtime environment 433 on top of the Android object-oriented application framework. Dalvik virtual machine 431 is a register-based virtual machine, and runs a compact executable format that is designed to reduce memory usage and processing requirements. Applications running on Android OS 430 include home screen 451, email application 452, phone application 453, browser application 454, and/or other application(s) (“App(s)”) 455.

For these reasons, applications written for Android do not generally run on desktop Linux distributions such as Hydroid OS 660 and applications written for standard Linux distributions do not generally run on Android OS 430. In this regard, applications for Android OS 430 and Hydroid OS 660 are not bytecode compatible, meaning compiled and executable programs for one do not run on the other.

FIG. 5 illustrates modified Android kernel 520 in more detail, according to various embodiments. Modified Android kernel 520 includes touch-screen display driver 521, camera driver(s) 522, Bluetooth driver(s) 523, shared memory allocator 524, IPC driver(s) 525, USB driver(s) 526, WiFi driver(s) 527, I/O device driver(s) 528, and/or power management module 529. I/O device driver(s) 528 includes device drivers for external I/O devices, including devices that may be connected to mobile computing device 110 through port 120. Modified Android kernel 520 may include other drivers and functional blocks including a low memory killer, kernel debugger, logging capability, and/or other hardware device drivers.

FIG. 6 illustrates Hydroid OS 660 in more detail, according to various embodiments. Hydroid is a full Linux OS that is capable of running almost any application developed for standard Linux distributions. In particular, libraries layer 662 of Hydroid OS 660 includes Linux libraries that support networking, graphics processing, database management, and other common program functions. For example, user libraries 662 may include the standard Linux C library (glibc) 664, Linux graphics libraries 662 (e.g., GTK, etc.), Linux utilities libraries 661, Linux database libraries, and/or other Linux user libraries. Applications run on Hydroid within an X-Windows Linux graphical environment using X-Server 674, window manager 673, and/or desktop environment 672. Illustrated applications include word processor 681, email application 682, spreadsheet application 683, browser 684, and other application(s) 685.

In one embodiment, Hydroid OS 660 includes components of a cross-environment communication framework that facilitates communication with Android OS 430 through shared kernel 520. These components include IPC library 663 that includes the base classes for the Binder IPC mechanism of the Android OS and remote communications service 671.

In one embodiment, Hydroid OS 660 is run within a chrooted (created with the ‘chroot’ command) secondary execution environment created within the Android root environment. Processes and applications within Hydroid OS 660 are run within the secondary execution environment such that the apparent root directory seen by these processes and applications is the root directory of the secondary execution environment. In this way, Hydroid OS 660 can run programs written for standard Linux distributions without modification because Linux user libraries 662 are available to processes running on Hydroid OS 660 in the chrooted secondary execution environment.

FIG. 7 illustrates an exemplary boot procedure 700 that may be used to boot up the components of OS architecture 300. Boot procedure 700 begins at step 702 when the system is powered on via hardware. For example, the user may turn on mobile computing device 110 via a switch or button.

At step 704, the boot loader is loaded in memory (e.g., RAM) with boot arguments passed from hardware or firmware. At step 706, the boot loader sets up the root file system. At step 708, the boot loader configures the memory and network support. In this step, the boot loader may also configure modem support, low memory protection, and security options. At step 710, the boot loader locates shared kernel 320 and loads it to memory, passing kernel arguments as needed. The boot loader starts shared kernel 320, at which point shared kernel 320 takes over control of the boot procedure. In one embodiment, shared kernel 320 is modified Android kernel 520.

At step 712, shared kernel 320 initializes drivers for hardware devices. In this step, shared kernel 320 may also initialize memory protection, virtual memory modules, and schedule caching. At step 714, shared kernel 320 initializes the mobile OS. In one embodiment, the shared kernel runs a user space initialization process to initialize Android OS 430. The initialization process reads a configuration file which describes system services and additional system parameters for Android OS 430. At step 716, the mobile OS framework is started, this generally includes starting runtime environments. In one embodiment, the root process of Android OS 430, Zygote, is run by the initialization process and initializes the Dalvik Virtual Java Machine runtime environment. At step 718, service(s) 344 for the mobile OS are started. Service(s) 344 for the mobile OS generally include telephony services, camera services, GPS services, and/or communications services. In one embodiment, Zygote starts the main Android SystemServer of Android OS 430 which starts Android services such as telephony, camera, Bluetooth, etc.

At step 720, the desktop OS is initialized. In one embodiment, an initialization process of Android OS 430 parses a second configuration file and executes the commands and runs the services configured in the second configuration file. At step 722, a desktop monitor service is started in the mobile OS that starts and monitors the desktop OS. In one embodiment, desktop monitor service 446 is started in Android OS 430. At step 724, the desktop monitor service establishes a separate execution environment for the desktop OS. In one embodiment, desktop monitor service 446 of Android OS 430 uses the Linux chroot command to setup the separate execution environment within the root file system for Hydroid OS 660. A separate execution environment for the desktop OS allows, for example, the desktop OS to have different user libraries than the mobile OS. In one embodiment, user libraries 662 of Hydroid OS 660 are in a separate execution environment of user libraries 432 of Android OS 430. Specifically, applications and programs in each OS can statically or dynamically link to libraries separately within each OS, without linking conflicts or library compatibility problems. At step 726, the desktop monitor service starts the desktop OS service(s) 374. In one embodiment, this includes the X-Window system 674 and Xfce desktop environment 672 of Hydroid OS 660. After step 726, mobile OS 130 and desktop OS 160 are running concurrently and independently on shared kernel 320 on mobile computing device 110.

If mobile computing device 110 is being used on its own without a secondary terminal environment, desktop OS 160 is not being used by the user. In this instance, desktop OS 160 can be suspended. For example, FIG. 9 illustrates OS architecture configuration 300 a where desktop OS 160 is in a suspended state. In OS architecture configuration 300 a, desktop OS 160, and processes within desktop OS 160 including window manager 972 and applications 382 and 384, are indicated as suspended by being represented by dashed lines.

If mobile computing device 110 is then docked with a secondary terminal environment having a user experience profile associated with a desktop OS, desktop OS 160 can be resumed and associated with the secondary terminal environment. While desktop OS 160 is suspended, processes and services of desktop OS 160 are suspended. Accordingly, these processes and services do not consume processing resources of mobile computing device 110. However, these processes and services maintain their variables and states such that they may be resumed where they left off when desktop OS 160 is resumed. Therefore, the user does not lose data they were working on in desktop OS 160 when it is suspended. In some embodiments, the current states of the suspended processes and services of desktop OS 160 are written to disk when desktop OS 160 is suspended.

In OS architecture 300, a service of mobile OS 130 reacts to docking events, controls the suspending and resuming of desktop OS 160, and configures mobile OS 130 or desktop OS 160 for a docked secondary terminal environment. As illustrated in FIG. 9, desktop monitor service 944 of mobile OS 130 reacts to docking events, suspends or resumes desktop OS 160, and configures mobile OS 130 or desktop OS 160 for docked secondary terminal environments.

FIG. 8 illustrates process flow 800 that may be employed by desktop monitor service 944 for detecting and responding to docking events. Process flow 800 is started at step 810 after boot procedure 700 completes and mobile OS 130 and desktop OS 160 are running concurrently and independently on shared kernel 320. At step 822, desktop monitor service 944 determines whether mobile computing device 110 is docked with a secondary terminal environment. Referring to FIG. 1, mobile computing device is docked with a secondary terminal environment when it is connected through port 120 to one or more I/O devices 144, 146 and/or 148 that make up secondary terminal environment 140.

If, at step 822, mobile computing device 110 is not docked with a secondary terminal environment through port 120, for example, if mobile computing device 110 is being used on its own, desktop monitor service 944 proceeds to step 724. At step 824, desktop monitor service 944 determines whether desktop OS 160 is suspended. As described above, after boot procedure 700 completes at step 726, desktop OS 160 is running concurrently with mobile OS 130 on shared kernel 320. Therefore, when process flow 800 is run after boot procedure 700, desktop OS 160 is not suspended at step 824. Desktop monitor service 944 then proceeds to step 826 where it suspends desktop OS 160. Once desktop OS 160 is suspended, process flow 800 completes at step 834.

As described above, FIG. 9 illustrates OS architecture configuration 300 a that corresponds to OS architecture 300 when mobile computing device 110 is not docked with a secondary terminal environment, according to various embodiments. In OS architecture configuration 300 a, desktop OS 160 is in a suspended state. While other processes of desktop OS 160 are in a suspended state, daemon process 974 of desktop OS 160 continues to run. Daemon process 974 may do background functions such as networking and/or performing other background tasks. Daemon process 974 may also maintain a list of process ids that are running and suspended in desktop OS 160. In some embodiments, daemon process 974 may be replaced by a service that performs these functions.

Desktop monitor service 944 communicates with daemon process 874 through an IPC channel in shared kernel 320. In embodiments, the IPC channel includes IPC driver 926 in shared kernel 320. Daemon process 974 registers to receive communications through an instantiated IPC protocol of the IPC channel. Desktop monitor service 944 uses the instantiated IPC protocol to pass messages through IPC driver 926 to daemon process 974. In one embodiment, Desktop monitor service 944 communicates with daemon process 974 through a cross-environment communications framework. In this embodiment, the cross-environment communication framework includes IPC library 433 of Android OS 430, IPC library 663 of Hydroid OS 660, and IPC driver 525 of Android kernel 520. IPC libraries 433 and 663 provide the base classes for an instantiation of an IPC protocol for cross-environment communication. Embodiments of the cross-environment communications framework are described in more detail in co-pending U.S. patent application Ser. No. ______, Attorney Dkt. No. 50224-01308, filed *Date*, entitled “Cross-Environment Communications Framework,” the entire contents of which are incorporated herein by reference.

Referring back to step 826 of process flow 800, desktop monitor service 944 suspends desktop OS 160 by communicating with daemon process 974 through the instantiated IPC protocol. Specifically, desktop monitor service 944 sends a call to a remotable object through the instantiated IPC protocol. The call includes actions to be performed by daemon process 974 to suspend desktop OS 160. In this regard, desktop monitor service 944 runs a remote procedure call in daemon process 974 to suspend desktop OS 160 at step 826 of process flow 800.

Process flow 800 is repeated when mobile computing device 110 is docked to a secondary terminal environment or undocked from a secondary terminal environment. A dock event occurs when device driver(s) in shared kernel 320 detect the dock event and notify mobile OS 130 that a dock event has occurred. In one embodiment, Android kernel 520 places the event into the event queue of Android OS 430. In this embodiment, Android OS 430 broadcasts a notification of the docking event to applications and services of Android OS 430. Desktop monitor service 944 then begins process flow 800 at step 820. At step 822, desktop monitor service 944 determines whether mobile computing device 110 is docked with a secondary terminal environment. If, at step 822, desktop monitor service 944 detects that mobile computing device 110 is docked to a secondary terminal environment, desktop monitor service 944 proceeds to step 828.

At step 828, desktop monitor service 446 determines whether a user experience profile of the docked secondary terminal environment is associated with a mobile OS or a desktop OS. In one embodiment, a dock connector used to connect mobile computing device 110 to secondary terminal environment 140 through port 120 includes a mechanical or electrical feature that indicates whether the user experience profile of the secondary terminal environment 140 is associated with a mobile OS or a desktop OS. For example, mobile computing device 110 may receive an electrical signal through port 120 that indicates by way of a voltage level or series of signal voltage levels whether the user experience profile of secondary terminal environment 140 is associated with mobile OS 130 or desktop OS 160. In other embodiments, desktop monitor service 944 can determine the user experience profile from predetermined criteria of I/O devices 144, 146, and/or 148 that make up secondary terminal environment 140. For example, the user experience profile of a tablet-style secondary terminal environment that includes a touch-screen that is used as a display and a primary input device may be associated with mobile OS 130. As another example, if secondary terminal environment 140 includes a display monitor having a display size or resolution greater than a predetermined value, secondary terminal environment 140 may be determined to have a user experience profile associated with desktop OS 160. Alternatively, if secondary terminal environment 140 includes a physical keyboard and/or pointing device(s), secondary terminal environment 140 may be determined to have a user experience profile associated with desktop OS 160.

User experience profiles of secondary terminal environments may also be user-selectable. For example, the user could associate particular criteria of I/O devices 144, 146, and/or 148 with user experience profiles associated with mobile OS 130 or desktop OS 160. For example, the user could associate particular I/O devices or combinations of I/O devices with a desktop user experience profile associated with desktop OS 160.

User experience profiles of secondary terminal environments may also be dynamically configurable. For example, desktop monitor service 944 may suggest a user experience profile for a secondary terminal environment based on past selections of user experiences for secondary terminal environments by the user. Desktop monitor service may then use a response by the user to the suggested user experience profile to update criteria used to determine suggested user experience profiles.

If, at step 828, desktop monitor service 944 determines that the docked secondary terminal environment has a user experience profile associated with mobile OS 130, desktop monitor service 944 proceeds to step 824. In one embodiment, an electrical signal from the dock connector of the docked secondary terminal environment indicates that the user experience profile of the docked secondary terminal environment is associated with mobile OS 130.

If, at step 828, desktop monitor service 944 determines that the docked secondary terminal environment has a user experience profile associated with desktop OS 160, desktop monitor service 944 proceeds to step 830. In one embodiment, an electrical signal from the dock connector of the docked secondary terminal environment indicates that it has a user experience profile associated with desktop OS 160.

At step 830, desktop monitor service 944 determines whether desktop OS 160 is suspended. If desktop OS 160 is not suspended, desktop monitor service 944 completes process flow 800 at step 834. If desktop OS 160 is suspended, desktop monitor service 944 resumes desktop OS 160 at step 832. In one embodiment, desktop monitor service 944 sends a call to a remotable object through the instantiated IPC protocol. The call includes actions to be performed by daemon process 974 to resume desktop OS 160. In this regard, desktop monitor service 944 runs a remote procedure call in daemon process 974 to resume desktop OS 160 at step 832. Process flow 800 then completes at step 834.

FIG. 10 illustrates OS architecture configuration 300 b in which mobile computing device 110 is docked with tablet-style secondary terminal environment 1040, according to various embodiments. Tablet-style secondary terminal environment 1040 includes port 1042, touch-screen display 1044, and other I/O devices 1046.

In OS architecture configuration 300 b, mobile OS 130 is associated with tablet-style secondary terminal environment 940 while desktop OS 160 is suspended. Mobile OS frame buffer 916 is configured for the resolution of touch-screen display 1044 and drives a video signal to touch-screen display 1044 through port 120. Input commands from I/O devices 1046 of secondary terminal environment 1040 are input to mobile computing device 110 through port 120 and handled by I/O device drivers 924. Components of mobile OS 130 including window manager 942 then accept the input commands. In this way, the user is presented with the mobile computing experience of mobile OS 130 through tablet-style secondary terminal environment 1040 in OS architecture configuration 300 b.

FIG. 11 illustrates OS architecture configuration 300 c in which mobile computing device 110 is docked with secondary terminal environment 1140 with a user experience profile associated with desktop OS 160. Secondary terminal environment 1140 includes port 1142, display monitor 1144, keyboard 1146, and/or pointing device(s) 1148.

In OS architecture configuration 300 c, mobile OS 130 is associated with the I/O devices of mobile computing device 110 including touch-screen display 116 and other I/O devices 118. Specifically, mobile OS 130 drives touch-screen display 116 through frame buffer 916 associated with mobile OS 130. Touch-screen driver 922 receives input commands from touch-screen display 116 and generates events that are handled by window manager 942 and other components of mobile OS 130.

In OS architecture configuration 300 c, desktop OS 160 is associated with secondary terminal environment 1140 through port 120. Specifically, desktop OS 160 drives display monitor 1144 through frame buffer 818 associated with desktop OS 160. I/O device driver(s) 924 of shared kernel 320 receive input commands from input device(s) of secondary terminal environment 1140. Because mobile OS 130 and desktop OS 160 are running concurrently on shared kernel 320, input commands received by I/O device driver(s) 924 are available in shared kernel 320 to both mobile OS 130 and desktop OS 160. Desktop OS 160 accepts the input commands received by I/O device driver(s) 924 while mobile OS 130 ignores these commands.

FIG. 12 shows an exemplary computing environment 1200 in which OS architecture configuration 300 c may be employed, according to various embodiments. In computing environment 1200, mobile OS 130 provides a mobile computing experience through the I/O devices of mobile computing device 110. Specifically, the user can interact with mobile OS 130 through mobile OS GUI 132 on touch-screen 116 and other I/O devices 118 that are integrated in mobile computing device hardware 112 of mobile computing device 110.

At the same time, desktop OS 160 provides a complete desktop computing experience through secondary terminal environment 1040. As illustrated in FIG. 12, secondary terminal environment 1140 includes dock cradle 1141. Dock cradle 1141 includes port 1142 (not illustrated) that is connected to mobile computing device through interface 122. Dock cradle 1141 is connected through interface 1143 to display monitor 1144, keyboard 1146, and/or pointing device(s) 1148. FIG. 12 illustrates that desktop OS GUI 162 is displayed on display monitor 1144 of secondary terminal environment 1140. Applications 382 and 384, running on desktop OS 160, may be displayed in application windows 1282, 1284, and/or 1286 within desktop OS GUI 162.

As described above, in one embodiment an Android mobile OS and a Linux desktop OS (“Hydroid”) run concurrently on the same shared kernel of a single mobile computing device. The Android mobile OS provides a mobile computing experience through mobile computing hardware and the Linux desktop OS provides a desktop computing experience through a secondary terminal environment having a user experience profile associated with the Linux OS. However, other OS combinations are contemplated as within various embodiments of the invention. For example, various aspects of the invention may be used to run Windows Mobile and Windows 7 on a shared kernel or sharing common kernel-mode processes. As another example, iOS and Mac OS X running on a shared kernel is also within the scope of various embodiments. Furthermore, aspects of the invention may be used advantageously by combinations of embedded OS's and desktop or mobile OS's running on a shared kernel.

The foregoing description has been presented for purposes of illustration and description. Furthermore, the description is not intended to limit embodiments of the invention to the form disclosed herein. While a number of exemplary aspects and embodiments have been discussed above, those of skill in the art will recognize certain variations, modifications, permutations, additions, and sub-combinations thereof.

The various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and/or software component(s) and/or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor.

The various illustrative logical blocks, modules, and circuits described may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array signal (FPGA), or other programmable logic device (PLD), discrete gate, or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The steps of a method or algorithm described in connection with the present disclosure, may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in any form of tangible storage medium. Some examples of storage media that may be used include random access memory (RAM), read only memory (ROM), flash memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM and so forth. A storage medium may be coupled to a processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. A software module may be a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media.

The methods disclosed herein comprise one or more actions for achieving the described method. The method and/or actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and/or use of specific actions may be modified without departing from the scope of the claims.

The functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions on a tangible computer-readable medium. A storage medium may be any available tangible medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM, or other optical disk storage, magnetic disk storage, or other magnetic storage devices, or any other tangible medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.

Thus, a computer program product may perform operations presented herein. For example, such a computer program product may be a computer readable tangible medium having instructions tangibly stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein. The computer program product may include packaging material.

Software or instructions may also be transmitted over a transmission medium. For example, software may be transmitted from a website, server, or other remote source using a transmission medium such as a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology such as infrared, radio, or microwave.

Further, modules and/or other appropriate means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or base station as applicable. For example, such a device can be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, various methods described herein can be provided via storage means (e.g., RAM, ROM, a physical storage medium such as a CD or floppy disk, etc.), such that a user terminal and/or base station can obtain the various methods upon coupling or providing the storage means to the device. Moreover, any other suitable technique for providing the methods and techniques described herein to a device can be utilized.

Other examples and implementations are within the scope and spirit of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations. Also, as used herein, including in the claims, “or” as used in a list of items prefaced by “at least one of indicates a disjunctive list such that, for example, a list of “at least one of A, B, or C” means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Further, the term “exemplary” does not mean that the described example is preferred or better than other examples.

Various changes, substitutions, and alterations to the techniques described herein can be made without departing from the technology of the teachings as defined by the appended claims. Moreover, the scope of the disclosure and claims is not limited to the particular aspects of the process, machine, manufacture, composition of matter, means, methods, and actions described above. Processes, machines, manufacture, compositions of matter, means, methods, or actions, presently existing or later to be developed, that perform substantially the same function or achieve substantially the same result as the corresponding aspects described herein may be utilized. Accordingly, the appended claims include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or actions. 

1. A method for configuring a mobile computing device to multiple user environments, the mobile computing device running a mobile operating system in a first execution environment on a shared kernel and running a desktop operating system in a second execution environment concurrently on the shared kernel, the method comprising: detecting, in the mobile computing device, a docking event of the mobile computing device with a secondary terminal environment; determining that a user experience profile of the docked secondary terminal environment is associated with the desktop operating system; and resuming, in response to determining that the user experience profile of the docked secondary terminal environment is associated with the desktop operating system, the desktop operating system from a suspended condition.
 2. The method of claim 1, wherein the step of determining that a user experience profile of the docked secondary terminal environment is associated with the desktop operating system comprises: receiving, in a desktop monitor service of the mobile operating system, a notification of a docking event from the shared kernel; and determining, by the desktop monitor service, that the user experience profile of the docked secondary terminal environment is associated with the desktop operating system.
 3. The method of claim 1, wherein the step of resuming the desktop operating system from a suspended condition comprises: receiving, in a daemon process of the desktop operating system, a call to a remotable object, the call to the remotable object including an action; and performing the action in the daemon process of the desktop operating system.
 4. The method of claim 1, wherein the step of determining the user experience profile of the secondary terminal environment includes receiving an indicator of the user experience profile of the secondary terminal environment from a dock connector.
 5. The method of claim 1, wherein the step of determining the user experience profile of the secondary terminal environment is based on predefined criteria associated with one or more input or output devices of the secondary terminal environment.
 6. The method of claim 5, wherein the predefined criteria include a resolution of a display device of the secondary terminal environment.
 7. The method of claim 5, wherein the predefined criteria include character input device type criteria.
 8. The method of claim 1, further including associating the desktop operating system with the docked secondary terminal environment.
 9. The method of claim 1, wherein the secondary terminal environment includes a display device, a keyboard, and a pointing device.
 10. A method for configuring a mobile computing device to multiple user environments, the mobile computing device concurrently running a mobile operating system in a first execution environment on a shared kernel and a desktop operating system in a second execution environment on the shared kernel, the method comprising: registering a daemon process of the desktop operating system through an inter-process communication channel in the shared kernel to receive remotable objects from a desktop monitor service of the mobile operating system; detecting a docking event of the mobile computing device with a secondary terminal environment; notifying the desktop monitor service of the mobile operating system of the docking event; determining, by the desktop monitor service, an action to be performed by the daemon process of the desktop operating system based on a user experience profile of the docked secondary terminal environment; and sending, from the desktop monitor service to the daemon process of the desktop operating system through the inter-process communication channel, the action to be performed.
 11. The method of claim 10, wherein the user experience profile of the docked secondary terminal environment is associated with the desktop operating system and the action to be performed comprises resuming the desktop operating system from a suspended condition.
 12. The method of claim 11, further including associating the docked secondary terminal environment with the desktop operating system.
 13. The method of claim 11, wherein the user experience profile of the docked secondary terminal environment is associated with the mobile operating system and the action to be performed comprises suspending the desktop operating system.
 14. The method of claim 13, further including associating the docked secondary terminal environment with the mobile operating system.
 15. A method for configuring a mobile computing device to multiple user environments, the mobile computing device running a mobile operating system in a first execution environment on a shared kernel and running a desktop operating system in a second execution environment concurrently on the shared kernel, the method comprising: detecting, in the mobile computing device, a docking event of the mobile computing device with a secondary terminal environment; determining that the mobile computing device is not docked to a secondary terminal environment; and suspending, in response to determining that the mobile computing device is not docked to a secondary terminal environment, the desktop operating system.
 16. The method of claim 15, wherein the docking event comprises undocking the mobile computing device from a secondary terminal environment.
 17. The method of claim 15, wherein the step of suspending the desktop operating system comprises: receiving, in a daemon process of the desktop operating system, a call to a remotable object, the call to the remotable object including an action; and performing the action in the daemon process of the desktop operating system. 